Rhapsody Developer Release Notes:
Installation

These notes are for the Rhaspody installation process, including the installation tools that are used to boot the system from a CD, install a base system, and install packages and updates to the system.

Notes Specific to Rhapsody Developer Release

New Features

Installer.app (in /System/Administration) now uses the gnutar tool to create and read packages. OpenStep packages created with tools that predate the Rhapsody Developer Release do not work with the Installer application included with Rhapsody.
BuildDisk.app (in /System/Administration) no longer displays the percentage complete as an absurdly high number. The application also now installs on drives larger than 4 GB.
Many of the command-line tools have been given autorelease pools, which enhances their performance.
Installing packages using the installer.sh script (in /usr/bin) is described in the release note Creating and Installing Packages.

Installing "Fat" Developer Libraries

After installing the system, insert the installation CD. As root enter the following in a Terminal shell:

cd CD name/NextCD/Packages
installer.sh --verbose DeveloperLibs.pkg

The script prints out a few lines stating the status of the installation. Upon completion of the installer script, press Command-Power to get the Restart panel. Then enter "r" to reboot the system.

The reboot is necessary because the System.framework shared library changed and the system's dynamic linker has invalid offsets to the old System.framework.

Setting up a Zynx Card

The driver for the Zynx single- or multi-port Ethernet card is included in the Developer Release 2 (DR2). It is not enabled however. To enable the drive, you must edit the /etc/startup/0300_Devices file. Add the line "driverLoader D=SwitchEthernets" after the "driverLoader D=Floppy" line. Save the file and reboot, this should automatically launch the driver if the card is present during booting.

Using the Serial Ports

To use the serial drivers with DR2 you must first enable them. First obtain the lastest release of the drivers, if necessary from Apple's Rhapsody Developer Release web site (http://devworld.apple.com/rhapsody/). After downloading it to your Rhapsody machine as root, untar it and place it in the /private/Drivers/ppc directory. To untar it, give a command in a Terminal shell similar to the following:

gnutar -xzvf ./drvPPCSerialPort.tar.gz /private/Drivers/ppc/ .

After loading the new driver, you must edit the /etc/startup/0300_Devices file to enable the driver. Add the line "driverLoader D=PPCSerialPort" before the "driverLoader D=PortServer" line. Save the file and reboot. The driver should automatically launch at boot time.

Known Problems

Setup Assistant: You must complete all of the pages of the Setup Assistant at the end of an installation. If you quit before you reach the final page, you will not be able to log into the computer. Your only recourse if this happens is to re-install Rhapsody. (Reference 2224444)
You should use the BuildDisk application only as part of the initial installation of the operating system. You should not run it after installation to install packages. Instead use /System/Administration/Installer.app or, if that is unavailable, the script /usr/bin/installer.sh.
Free space partitions located immeadiately before the destination HFS partition for installing confuse the installer script.
A related problem prevents installation on the last partition created on a drive formatted with LaCie SilverLining. You can either install into another HFS partition, or use SilverLining to repartition the disk so that the destination partition for installation is not the last one on the disk. Do this by splitting the last partition into two partitions, one almost the same size as the existing partition, and the second a very small partition that occupies the last spot in the partition map. You can also install onto a dedicated external drive (this is the recommended course).
Windows only: When you run the SETUP.EXE program, make sure that there are no spaces in your PATH environment variable. If there are spaces in PATH, the SETUP program replaces the PATH variable instead of modifying it. To work around this problem, use directory names that comform to the "8.3" standard; you can find the 8.3 name of a directory in the Windows Explorer Properties panel for the directory. For example, instead of using C:\Program Files\WindowsNT you should use C:\Progra~1\WindowsNT.
Windows only: After installing Rhapsody, ensure that there is no CLASSPATH variable defined in the System environment or in an AUTOEXEC.BAT file in the root directory of your boot drive. If you have any user-defined class paths, ensure that they are merged correctly into the CLASSPATH variable defined in the User environment.